Repository navigation
Conversation
rwgk
added
enhancement
Contributor
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
This was referenced Oct 21, 2026
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
2 times, most recently
from
October 21, 2026 13:57
6cd44d1 to
cce0618
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
from
October 21, 2026 14:09
cce0618 to
32cb766
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
2 times, most recently
from
October 21, 2026 17:27
052a600 to
5a66951
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
2 times, most recently
from
October 21, 2026 19:33
a9fe883 to
d5cec61
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
from
October 22, 2026 03:52
d5cec61 to
7d6d297
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
from
October 22, 2026 04:15
7d6d297 to
c860fc8
Compare
mdboom
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
from
October 23, 2026 15:04
c860fc8 to
4b4679c
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
3 times, most recently
from
October 26, 2026 21:35
a4feb26 to
9f2d183
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
from
October 27, 2026 00:23
9f2d183 to
c2720b9
Compare
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
from
October 30, 2026 03:20
c2720b9 to
133aa17
Compare
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
codex on behalf of Ralf: Run release resolution, note checks and publishing tools with the hardened workflow-owned interpreter. Keep tagged sources isolated and preserve no-checkout package verification. Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
rwgk
force-pushed
the
rwgk/cb12-on-main-06-release-routing
branch
from
November 1, 2026 22:50
9c9ba92 to
4983cc7
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
— Claude Fable 5.1 on behalf of Ralf —
Layer 6 of 8. Previous: #3176. Next: #3178. Stack map at the bottom.
What this PR does
Makes releases follow the tagged source's configuration, so
v12.9.Nandv13.4.Ntags can both be released frommain's workflow.The one idea to hold on to: the release workflow supplies tools; the tag supplies configuration. A new
resolve-bindings-packagejob checks out the tag intorelease-source/, reads itsci/versions.yml, and decides package root and toolkit. The workflow revision never substitutes its own pins, layout, or release notes. Tags from before the registry (schema 2) are rejected and need the13.4.xbranch tooling instead.release.yml: resolution job;run-idis validated (same tag, same SHA, successful push run) instead of trusted; tag existence verified before a draft is created; the resolved package flows into docs, upload, TestPyPI, and PyPI jobs.release-upload.yml: separate control-plane and release-source checkouts; archive fromrefs/tags/....ci/tools/validate_release_wheels.py(new; replaces the shell wrapper): the complete wheel matrix (Python versions x platforms from the tagged source) must be present; dev/local versions and duplicates are rejected.ci/tools/check_release_notes.py: notes must exist for the exact version in the tagged source;.postNexempt; Pathfinder keeps its own rule; thebackport_branchlogic is gone.ci/tools/lookup-run-id:--run-idvalidation for tag mode.RELEASE-core.mddescribe dry run, thenfull-release.After this merges
v12.9.Ntag onmain(or a release branch containing the registry) can be released with CI: Release, componentcuda-bindingsthencuda-python.mainkeep working; dry runs for pre-registry tags (such asv13.4.4) must be dispatched from the13.4.xbranch after that branch receives the current CI security fixes.Where to look
.github/workflows/release.yml:resolve-bindings-packageanddetermine-run-id.ci/tools/validate_release_wheels.pyandci/tools/check_release_notes.py: what can reach PyPI..github/RELEASE-core.md: the operator's view (the bindings guide arrives in cuda.bindings: document shared maintenance and release branches #3178).All changes (10 files, +1,046 / -698)
.github/workflows/release.yml,.github/workflows/release-upload.yml,.github/ISSUE_TEMPLATE/release_checklist.yml,.github/RELEASE-core.md,ci/tools/check_release_notes.py,ci/tools/lookup-run-id,ci/tools/validate_release_wheels.py(new),ci/tools/validate-release-wheels(deleted),ci/tools/tests/test_check_release_notes.py,ci/tools/tests/test_validate_release_wheels.py(new).Validation and what has not been exercised
341d286d(run 40997121153, attempt 3, 105 jobs). Pre-commit passes at the current head.Stack map: review scopes and merge units
cuda_bindings_12/, byte-identical to the12.9.xbranchmain; planner; version preview bootstrapbackport_branchLayers 3 to 5 are review boundaries, not working intermediate states: #3174 alone breaks CI (workflows still read the removed
cuda.build.version), and #3175 alone fails actionlint (callers pass an input the test workflows only accept in #3176). The plan is to review them separately and land the reviewed group as one merge. #3176 is the full-CI target for the group.The staged stack #3314-#3322 is the alternative in which every layer is mergeable on its own; both stacks reach the same end state, except that the staged stack keeps compatibility routes for older artifact sources and retained CUDA 13 tags.